From: kaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Date: Thu, 29 Sep 2005 16:12:48 +0000 (+0100)
Subject: Update GDB server documentation for crashed guests.
X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~16769^2~5
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=ef037063069e69831f7d6d6d4add8fb5b9a99562;p=xen.git

Update GDB server documentation for crashed guests.
Signed-off-by: Keir Fraser <keir@xensource.com>
---

diff --git a/tools/debugger/gdb/README b/tools/debugger/gdb/README
index 43f1e60fef..0aa9d68772 100644
--- a/tools/debugger/gdb/README
+++ b/tools/debugger/gdb/README
@@ -20,10 +20,18 @@ To build a debuggable guest kernel image:
 
 To debug a running guest:
  1. Use 'xm list' to discover its domain id ($domid). 
- 2. Run 'gdbserver-xen 127.0.0.1:9999 --attach $domid'
- 3. Run 'gdb /path/to/vmlinux-syms-2.6.xx-xenU'
+ 2. Run 'gdbserver-xen 127.0.0.1:9999 --attach $domid'.
+ 3. Run 'gdb /path/to/vmlinux-syms-2.6.xx-xenU'.
  4. From within the gdb client session:
     # directory /path/to/linux-2.6.xx-xenU [*]
     # target remote 127.0.0.1:9999
     # bt
     # disass
+
+To debug a crashed guest:
+ 1. Add '(enable-dump yes)' to /etc/xen/xend-config.sxp before
+    starting xend.
+ 2. When the domain crashes, a core file is written to
+    '/var/xen/dump/<domain-name>.<domain-id>.core'.
+ 3. Run 'gdbserver-xen 127.0.0.1:9999 --file <core-file>'.
+ 4. Connect to the server as for a running guest.